src/benchmarks/gc/GC.Infrastructure/GC.Infrastructure.Core/Presentation/Microbenchmarks/Json.cs:15

• Json.Generate doesn’t use the configuration parameter, and the using GC.Analysis.API; / using GC.Infrastructure.Core.Presentation.GCPerfSim; directives are unused. Consider removing the unused parameter/usings to avoid warnings and keep the API surface minimal.

src/benchmarks/gc/GC.Infrastructure/GC.Infrastructure.Core/Analysis/Microbenchmarks/MicrobenchmarkResultComparison.cs:155

• When trace collection is enabled, tracePath falls back to an empty string if the JSON path isn’t present in jsonToTraceMap, and that empty path is passed to AnalyzerManager.GetAnalyzer(...), which will fail with a less actionable error. Prefer validating the mapping result (e.g., TryGetValue) and throwing an exception that includes the missing JSON path / benchmark name, or ensuring MapJsonToTrace guarantees coverage for every jsonPath.

                if ((!excludeTraces) && configuration.TraceConfigurations.Type != "none")
                {
                    string outputPathForRun = Path.Combine(configuration.Output.Path, run.Name!);
                    string tracePath = jsonToTraceMap.GetValueOrDefault(jsonPath, "");

                    using (var analyzer = AnalyzerManager.GetAnalyzer(tracePath))
                    {

src/benchmarks/gc/GC.Infrastructure/GC.Infrastructure.Core/Presentation/Microbenchmarks/Markdown.cs:181

• GetValueOrDefault(column) on Dictionary<string,double> returns 0 when the metric is missing, so baselineValue.HasValue is always true and missing metrics render as 0 (and deltaPercent can divide by 0). This can silently produce incorrect tables when a column can’t be computed (e.g., GC-derived columns when traces are unavailable). Use TryGetValue and treat missing metrics as null/empty, and guard the percent calculation when the baseline value is 0.

                        foreach (var column in configuration.Output.Columns)
                        {
                            double? baselineValue = lr.AveragedBaselineOtherMetrics.GetValueOrDefault(column);
                            double? comparandValue = lr.AveragedComparandOtherMetrics.GetValueOrDefault(column);

                            string baselineResult = baselineValue.HasValue ? Math.Round(baselineValue.Value, 4).ToString() : string.Empty;
                            string comparandResult = comparandValue.HasValue ? Math.Round(comparandValue.Value, 4).ToString() : string.Empty;
                            double? delta = baselineValue.HasValue && comparandValue.HasValue ? comparandValue.Value - baselineValue.Value : null;
                            string deltaResult = delta.HasValue ? Math.Round(delta.Value, 4).ToString() : string.Empty;

                            double? deltaPercent = delta.HasValue ? (delta / baselineValue.Value) * 100 : null;
                            string deltaPercentResult = deltaPercent.HasValue ? Math.Round(deltaPercent.Value, 4).ToString() : string.Empty;

src/benchmarks/gc/GC.Infrastructure/GC.Infrastructure.Core/Analysis/BdnJsonResult.cs:25

• The BDN JSON POCOs declare many non-nullable reference-type properties (e.g., HostEnvironmentInfo.BenchmarkDotNetCaption, Benchmark.Measurements, BdnJsonResult.Benchmarks) without initialization. With <Nullable>enable</Nullable>, this produces CS8618 warnings and also makes it easy for deserialization to yield nulls at runtime if fields are absent. Consider making these properties nullable where appropriate or initializing with = null!; / empty collections for required fields.